Skip to content

Conversation

cacieprins
Copy link
Contributor

@cacieprins cacieprins commented Oct 7, 2025

  • Closes

Additional details

  • migrates trigger-publish-binary-pipeline.js to an inlined bash script to speed it up and simplify it
  • adds a pipeline parameter that can be set via CircleCI UI to determine which branch we use in the publish-binary pipeline, to reduce file churn and human error
  • updates the packages/electron/README.md to include the simplified steps

This should reduce cognitive load regarding branches when performing Electron upgrades.

Steps to test

How has the user experience changed?

PR Tasks


Note

Introduces a CircleCI parameter to select the target publish-binary branch and replaces the Node trigger script with an inline bash command/command file, updating jobs and docs accordingly.

  • CI/CircleCI:
    • Parameters: Add publish-binary-branch pipeline parameter in .circleci/config.yml and @pipeline.yml; pass it via continuation to packed pipeline.
    • Trigger Command: Replace scripts/binary/trigger-publish-binary-pipeline.js with new command commands/trigger-publish-binary-pipeline.yml (bash-based) that triggers the cypress-publish-binary pipeline and accepts target-repo-branch.
    • Jobs: Update create-and-trigger-packaging-artifacts to call trigger-publish-binary-pipeline with target-repo-branch: << pipeline.parameters.publish-binary-branch >>.
  • Docs:
    • Update packages/electron/README.md checklist to use the new CircleCI parameter and workflow filter note instead of temporarily modifying the trigger script.

Written by Cursor Bugbot for commit b3cd415. This will update automatically on new commits. Configure here.

…ed value for branch

- migrates trigger-publish-binary-pipeline.js to an inlined bash script to speed
  it up and simplify it
- adds a pipeline parameter that can be set via CircleCI UI to determine which
  branch we use in the publish-binary pipeline, to reduce file churn and human
  error
- updates the packages/electron/README.md to include the simplified steps
- [ ] Temporarily update the circle configuration to allow `cypress` to run against the branch
- [ ] Temporarily set target `cypress-publish-binary` branch as a `branch` property on the request body in [../../scripts/binary/trigger-publish-binary-pipeline.js](../../scripts/binary/trigger-publish-binary-pipeline.js) script, so that you can test against this branch from the electron upgrade branch. This property must be set both at the root of the body object, and on the `parameters` key. If it is not set at the root, the binary pipeline will continue to use the primary branch.
- [ ] Add your branch name to the `&full-workflow-filters` anchor in [`@pipeline.yml`](../../.circleci/src/pipeline/@pipeline.yml)
Copy link
Contributor Author

@cacieprins cacieprins Oct 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this can be parameterized as well (separately, to reduce delta surface)

@cacieprins cacieprins self-assigned this Oct 7, 2025
@cacieprins cacieprins marked this pull request as ready for review October 10, 2025 14:32
@cacieprins cacieprins marked this pull request as draft October 10, 2025 14:33
cursor[bot]

This comment was marked as outdated.

@cacieprins cacieprins marked this pull request as ready for review October 10, 2025 14:39
cursor[bot]

This comment was marked as outdated.

@AtofStryker AtofStryker self-requested a review October 10, 2025 15:22
Copy link

cypress bot commented Oct 10, 2025

cypress    Run #66382

Run Properties:  status check failed Failed #66382  •  git commit b3cd415703: fix continuation json
Project cypress
Branch Review ci/parameterize-binary-branch
Run status status check failed Failed #66382
Run duration 46m 00s
Commit git commit b3cd415703: fix continuation json
Committer Cacie Prins
View all properties for this run ↗︎

Test results
Tests that failed  Failures 1
Tests that were flaky  Flaky 13
Tests that did not run due to a developer annotating a test with .skip  Pending 1102
Tests that did not run due to a failure in a mocha hook  Skipped 4
Tests that passed  Passing 26577
View all changes introduced in this branch ↗︎

Warning

Partial Report: The results for the Application Quality reports may be incomplete.

UI Coverage  45.69%
  Untested elements 184  
  Tested elements 159  
Accessibility  97.97%
  Failed rules  4 critical   8 serious   2 moderate   2 minor
  Failed elements 101  

Tests for review

Failed  cypress/e2e/studio/studio.cy.ts • 1 failed test • app-e2e

View Output

Test Artifacts
Cypress Studio > updates an existing test with assertions Test Replay Screenshots
Flakiness  e2e/origin/config_env.cy.ts • 1 flaky test • 5x-driver-electron

View Output

Test Artifacts
cy.origin- Cypress.config() > serializable > overwrites different values in secondary if one exists in the primary Test Replay
Flakiness  issues/28527.cy.ts • 1 flaky test • 5x-driver-electron

View Output

Test Artifacts
issue 28527 > fails and then retries and verifies about:blank is not displayed Test Replay Screenshots
Flakiness  e2e/origin/config_env.cy.ts • 1 flaky test • 5x-driver-chrome

View Output

Test Artifacts
cy.origin- Cypress.config() > serializable > overwrites different values in secondary if one exists in the primary Test Replay
Flakiness  issues/28527.cy.ts • 1 flaky test • 5x-driver-chrome

View Output

Test Artifacts
issue 28527 > fails and then retries and verifies about:blank is not displayed Test Replay Screenshots
Flakiness  e2e/origin/cookie_login.cy.ts • 1 flaky test • 5x-driver-firefox

View Output

Test Artifacts
... > past Max-Age, before Expires -> not logged in
    </td>
  </tr></table>

The first 5 flaky specs are shown, see all 13 specs in Cypress Cloud.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant